• 0 Votes
    16 Posts
    3k Views
    N

    @rtw915 said in WAN optimization/acceleration:

    Now the SQL team needs me to find a way to improve SQL linked server transfer rates to synchronize transactions.

    This will bring you back to the initial wan accelerator solution.
    The only other possible solution is to redesing the db subsystem, utilizing some way of sql replication, taking into consideration propagation delays

  • 0 Votes
    6 Posts
    2k Views
    D

    Yeah what confused me the most is that router->internet was testing at 750mbps+ with speedtest-cli, and desktop to router (through the same switch I'm normally connected through) was testing at 400+mbps (when downloading a dummy 1GB zip file I put in the web dir on the router... and it probably could have ramped up faster if it hadn't yanked the entire file in ~20 seconds).

    That's what got me looking at the router configuration itself, because obviously the router->internet connection was fine, and the PC->router connection was fine -- so it had to be something on the router itself that was bottlenecking things.

  • 0 Votes
    20 Posts
    13k Views
    johnpozJ

    Sorry but I am with @ITFlyer - and I edited your post to remove what amounts to keywords and a link..

    Glad your wanting to help - but keep it on topic to the question at hand.. And why would you join a forum, minutes latter add such a post to a almost year old thread, because it mentions something related to what your wanting to promote is what it looked like.

  • 0 Votes
    3 Posts
    2k Views
    T

    After contact with microsoft helpdesk I found the solution for me.
    For future reference: I had to turn on mss clamping and set it to 1350. This is also in the advanced IPSec settings

    Maybe this settings was defaulted after an update? I wasn't the one who configured it in the first place, so I wouldn't know for sure.

    I made sure to match my settings to this document https://docs.microsoft.com/nl-nl/azure/vpn-gateway/vpn-gateway-about-vpn-devices

    @stephenw10 Thanks for the reply, I had this disabled already, but the pointer was appreciated